-
-
Notifications
You must be signed in to change notification settings - Fork 7
[Merged by Bors] - Kerberos AD backend #254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Note before merging this: currently this disables TLS validation, need to let users supply a trust root instead. |
Successfully tested this branch against a Windows Server 2022 AD and stackabletech/hdfs-operator#334 |
I think I'm stupid and it actually tries to create
Do we want to improve the error message, so that we know which user can't be created?
|
There might have been a race condition, it can also happen if we fail to write the password back into K8s after creating the AD user... |
That sucks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did walk through the code.
Please don't forget to add a breaking changelog entry
I think I'd like to get the CRD change into 23.4, which would make the rest of this PR non-breaking when it does land. |
+1, was thinking the same |
# Description This should help prepare for making AD integration (#254) a non-breaking change. Co-authored-by: Natalie <[email protected]>
Regarding b25995d: Do we also want so support webpki as ca-cert validation mechanism (as we e.g. do for ldap server conections). Or would say 99% of the users run their AD behind their own pki? |
I would assume that private PKI is by far the norm. We can always go back and enable WebPKI support later, should the need arise. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this! Only two minor comments left
# ldapServer must match the AD Domain Controller's FQDN or GSSAPI authn will fail | ||
# You may need to set AD as your fallback DNS resolver in your Kube DNS Corefile | ||
ldapServer: addc.example.com | ||
passwordCacheSecret: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we please also document
ldapTlsCaSecret:
# namespace: default
name: secret-operator-ad-ca
Also that we will always use ldaps and the Secret needs the key ca.crt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tests/test-definition.yaml
Outdated
@@ -3,3 +3,6 @@ dimensions: [] | |||
tests: | |||
- name: kerberos | |||
dimensions: [] | |||
# Requires manual connection to an AD cluster | |||
- name: kerberos-ad |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to disable this test by default before merging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think that makes sense to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM % the documentation comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx!
bors r+ |
# Description Fixes #253 Co-authored-by: Sebastian Bernauer <[email protected]>
Pull request successfully merged into main. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Description
Fixes #253
Definition of Done Checklist
Once the review is done, comment
bors r+
(orbors merge
) to merge. Further information